Repository navigation
docs(WO17): py leg landed — the py parser is generated from the same pinned .parg; WO17 complete - #435
Merged
Conversation
…pinned .parg; WO17 complete
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
WO17's final piece landed: interscript-ruby #843 merged — the py parser is generated from the same sha256-pinned
.pargthe ts parser uses (module-for-module port: grammar_source / parg_reader / peg with match-span recording for the byte-exact override key and failure diagnostics / actions).parse_isc's public API unchanged; the ~900-line hand scanner replaced.Evidence: py-vs-py parity driver 434/434 identical-to-hand (canonical schema and raw field-for-field); the maps harness scores it exactly like the incumbent (411/434, same 23 files, zero status flips); the py failure set is byte-identical to a pristine origin/main run (18 pre-existing environment gaps); the golden additivity test replays green in-suite.
Owner-flagged: interpreter perf (434-file corpus ~86 s vs hand's ~7 s — closure-compilation follow-ups documented, semantics untouched), a fourth dormant grammar extension (use-in-pass splicing, py-suite-pinned), and the standing cross-runtime alignment decisions (
whenposition, dep-name lenience, U-escapes).WO17 is complete: all four steps landed. The
.parggrammar is the single semantic source for the ts and py parsers, judged continuously by the parity harness and the maps-CI four-runtime additivity gates.